Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "add -eou pipefail to remaining job templates" #6748

Merged

Conversation

bbguimaraes
Copy link
Contributor

Reverts #6738

teardown containers are not running properly, e.g.:

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/438/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws/2200/artifacts/e2e-aws/container-logs/teardown.log

(note that the jobs itself succeeded, which is another problem)

Reverting because CI is blocked.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 17, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 17, 2020
@petr-muller
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bbguimaraes, petr-muller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 5bbf0be into openshift:master Jan 17, 2020
@openshift-ci-robot
Copy link
Contributor

@bbguimaraes: Updated the following 35 configmaps:

  • prow-job-cluster-launch-installer-upi-src configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-upi-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml
  • prow-job-cluster-launch-e2e-openshift-ansible configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-e2e-openshift-ansible.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-openshift-ansible.yaml
  • prow-job-cluster-launch-installer-libvirt-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-openstack-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-openstack-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-openstack-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-scaleup-e2e-40 configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-scaleup-e2e-40.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-scaleup-e2e-40.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-e2e-openshift-jenkins configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-e2e-openshift-jenkins.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-openshift-jenkins.yaml
  • prow-job-cluster-scaleup-e2e-40 configmap in namespace ci at cluster default using the following files:
    • key cluster-scaleup-e2e-40.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-scaleup-e2e-40.yaml
  • prow-job-cluster-launch-installer-openstack-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-openstack-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-openstack-e2e.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-e2e-openshift-ansible configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-e2e-openshift-ansible.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-openshift-ansible.yaml
  • prow-job-cluster-launch-e2e-azure configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-e2e-azure.yaml using file ci-operator/templates/openshift/openshift-azure/cluster-launch-e2e-azure.yaml
  • prow-job-cluster-launch-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-e2e.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e.yaml
  • prow-job-cluster-launch-e2e-azure configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-e2e-azure.yaml using file ci-operator/templates/openshift/openshift-azure/cluster-launch-e2e-azure.yaml
  • prow-job-endurance-install configmap in namespace ci at cluster default using the following files:
    • key endurance-install.yaml using file ci-operator/templates/openshift/endurance/endurance-install.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-e2e-openshift-jenkins configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-e2e-openshift-jenkins.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-openshift-jenkins.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-endurance-install configmap in namespace ci-stg at cluster default using the following files:
    • key endurance-install.yaml using file ci-operator/templates/openshift/endurance/endurance-install.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-libvirt-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-libvirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-libvirt-e2e.yaml
  • prow-job-cluster-launch-installer-metal-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-metal-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-metal-e2e.yaml
  • prow-job-cluster-launch-e2e-upgrade configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-e2e-upgrade.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-upgrade.yaml
  • prow-job-cluster-launch-e2e-upgrade configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-e2e-upgrade.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e-upgrade.yaml
  • prow-job-cluster-launch-installer-upi-src configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-upi-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-src.yaml
  • prow-job-cluster-launch-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-e2e.yaml using file ci-operator/templates/openshift/openshift-ansible/cluster-launch-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-metal-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-metal-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-metal-e2e.yaml
  • prow-job-cluster-launch-installer-ovirt-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-ovirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-ovirt-e2e.yaml
  • prow-job-cluster-launch-installer-ovirt-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-ovirt-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-ovirt-e2e.yaml

In response to this:

Reverts #6738

teardown containers are not running properly, e.g.:

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/438/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws/2200/artifacts/e2e-aws/container-logs/teardown.log

(note that the jobs itself succeeded, which is another problem)

Reverting because CI is blocked.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@bbguimaraes bbguimaraes deleted the revert-6738-pipefail branch January 17, 2020 10:18
@openshift-ci-robot
Copy link
Contributor

@bbguimaraes: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift-cnv/cnv-ci/master/e2e-test 07bd61d link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-gcp/master/e2e-gcp-operator 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/fcos/e2e-vsphere 07bd61d link /test pj-rehearse
ci/rehearse/openshift/openshift-ansible/release-3.11/e2e-atomic 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-metal 07bd61d link /test pj-rehearse
ci/rehearse/openshift/cluster-api-provider-aws/master/e2e-aws-operator 07bd61d link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-gcp 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy 07bd61d link /test pj-rehearse
ci/rehearse/codeready-toolchain/host-operator/master/e2e 07bd61d link /test pj-rehearse
ci/rehearse/openshift/cluster-api-actuator-pkg/master/e2e-azure-operator 07bd61d link /test pj-rehearse
ci/rehearse/cri-o/cri-o/release-1.13/e2e-aws 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-ovirt 07bd61d link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-openstack 07bd61d link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-scaleup-rhel7 07bd61d link /test pj-rehearse
ci/prow/pj-rehearse 07bd61d link /test pj-rehearse
ci/rehearse/openshift/image-registry/release-3.11/e2e-gcp 07bd61d link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

wking added a commit to wking/ci-tools that referenced this pull request Jan 24, 2020
Bringing over a number of changes which have landed in
ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
as of openshift/release@c64d5d7d8f (Merge pull request #6845 from
wking/shared-subnets-for-other-regions, 2020-01-23).

One series was AWS region sharding:

* openshift/release@b7179335a3
  (ci-operator/templates/openshift/installer/cluster-launch-installer-*:
  Random AWS regions for IPI, 2020-01-23, openshift/release#6833).
* openshift/release@7e38260d25
  (ci-operator/templates/openshift/installer: Shared subnets for new
  regions, 2020-01-23, openshift/release#6845).

Another series was the password removal followed by a bunch of
pipefail fumbling ;)

* openshift/release@4847cb5477 (clean up install log output,
  2020-01-13, openshift/release#6692).
* openshift/release@5c6ca8a506 (templates: Use 'pipefail' so that grep
  doesn't mask install failures, 2020-01-15, openshift/release#6718).
* openshift/release@bee15b9fa8 (add -eou pipefail to remaining job
  templates, 2020-01-16, openshift/release#6738)
* openshift/release@07bd61d677 (Revert "add -eou pipefail to remaining
  job templates", 2020-01-17, openshift/release#6748).
* openshift/release@ca655477ca (Revert "Revert "add -eou pipefail to
  remaining job templates"", 2020-01-17, openshift/release#6750).
* openshift/release@9d7453156b (tolerate undefined env vars in
  teardown, 2020-01-17, openshift/release#6750).

And there was also:

* openshift/release@c6c2efb3fc (templates: Add ipv6 variant that
  triggers azure singlestack, 2020-01-22, openshift/release#6809).
* openshift/release@752455a47f (templates: fix check for unset
  variable, 2020-01-16, openshift/release#6723).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants